home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Dr. Windows 3
/
dr win3.zip
/
dr win3
/
WINSOUND
/
WDISC320.ZIP
/
RELEASE.TXT
< prev
next >
Wrap
Text File
|
1993-01-06
|
16KB
|
300 lines
=-=-=-=-=-=-=-=--=-=-=-==-=-=-WinDisc 3.20-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Release Notes:
Version 3.20 Features and Fixes:
- New parameter: running Windisc W will cause WinDisc to
wait for 10 seconds before trying to identify a disc
after it has been inserted. This will give the cd-rom
drive time to finish whatever it is that they do when
you insert a new disc (i.e. when you put the disc in
and the light goes on for a few seconds) before WinDisc
goes trying to get information from it. This should
help resolve problems in two areas:
1) Mis-identification - sometimes, WinDisc wouldn't
"realize" that a cd had been inserted, as the
drive was going through its reinitialization while
WinDisc was trying to get information, so what it
got back was a bunch of zeros - indicating no disc.
2) Crrrashhh! - Apparently, some systems would crash
when WinDisc tried to access the drive while it was
still initializing. The "W" parameter should solve
this too.
If anyone still has problems, please get in touch with me
(see the readme.txt file for information on how to reach
me) As I only have two systems at home to try this on, its
difficult to tell whether or not it'll work on others.
The only way for me to find out what does and doesn't work
is to hear from users!
- New option in setup dialog: Now in the setup dialog is
a checkbox for "Expanded SysMenu". Checking this option
will add the Disc Information, Jump To Track, and Volume
(if applicable) options to the system menu. This way,
you can click on the system menu, and be able to access
these dialogs without double clicking on the WinDisc
status screen. (Good when running WinDisc minimized)
- Timer Killed: In version 1.0 of WinDisc, is used timer
number 123, and in later versions number 5. Anyway, I was
initializing with timer 5, and trying to kill timer 123
when the program shut down. Oops. Now, however, I'm using
timer #1. As I understand it, if you use timer 1 in the
init, it will automatically detect the next available
one and use it. If this causes problems, I'll fix it in
the next version. (Maybe make the timer number an option)
* * * New registration algorithm: Registered users may notice
that their registration code is rather short. I will be
implementing a new registration code algorithm in the
_next_ version of WinDisc. Prior to its release, I'll be
sending registered users their new codes, so they don't
miss out.
Version 3.13a Fixes
- Oops, just before compiling version 3.13, I reinstalled
Borland Pascal, and forgot to adjust the memory options.
It seems as though some users were getting an error 202
(stack overflow, if I remember correctly) I have fixed
this by increasing the memory sizes...the problem should
be fixed now.
Version 3.13 Fixes
- Some users are still experiencing lockups. I think
this is cause by WinDisc checking to see if the device
supports software volume control. To test this theory,
I've added the "v" parameter, which skips volume control
checking. (And turns of volume control) This _should_
alleviate the problem, if, in fact, thats what the
problem was. Also, I'm now documenting the "d" parameter,
for debug mode. This parameter will cause WinDisc to
display several dialog boxes before the main window
appears. They will give information, as well as tell
what taks are being performed in order to get WinDisc
going. If you are having troubles getting the program
to run, please run it with the "d" parameter, have a
paper and pencil in hand, and write down what the
message boxes say <especially the final one, if it
locks up after getting to that point>.
Version 3.12 Fixes
- I (finally) figured out why the volume control didn't
work on some machines. It seems as though besides the
wDeviceID ID of the drive, there's also a separate
mci device ID, which you need to use for setting the
volume. I was using the wrong one! The mci device id
on *my* system is 3, and the wDeviceID id is 2. I
just assumed that you added 1 to the wDeviceID, and
it would work. Apparently not, as I heard from several
users. I happened to stumble across another bit of
code in the program where I was using the mci id, and
it hit me - duh! Everything works now.
Go ahead and try it now. If the volume control works,
good. If not, come back and read this next paragraph.
--- It doesn't apply to those who WinDisc functions properly
| for.
|
| |- - There's also a new feature...
| | Some people have their cd audio input coming from
| | a line-in jack, as opposed to the little cd-connector
|-| thingy. (The little plug with 4 wires, going from the
| cd rom drive to the sound card) Anyway, for those using
| the line-in jack, if you start WinDisc as follows:
|
| WinDisc L
|
|-It will use the line-in jack for volume control.
Version 3.11 Fixes
- Version 3.11 adds the MCI_WAIT flag to the operation
that initializes the CD-ROM drive. Before adding this,
WinDisc crashed when running under NDW 3.0. (And maybe
some other programs)
Version 3.10 Fixes
- 3.10 Changes the way animated icons are handled.
The result if this change is that the system won't
slow down very much when using the animated icons.
A "Jump to Track" dialog has been added, allowing
you to...jump to a selected track. This dialog
can be brough up by double clicking the Left mouse
button. The CD Info dialog is now accessed by
double clicking the middle mouse button (if present).
Version 3.02 Fixes
- Just added another animated icon.
Version 3.01 Fixes:
- 3.01 is basically a bug fix for 3.0. I seem
to have made a mistake somewhere that caused
WinDisc to lock up on some systems. I (think)
it has been corrected. There is also a new
feature: A setup dialog that lets you choose
a few options, including: The icon you'd like
displayed on your Windows desktop, whether or